Network slice selection assistance information configuration

ABSTRACT

Apparatuses, methods, and systems are disclosed for NSSAI configuration. One method includes determining a configured network slice selection assistance information for a public land mobile network for a remote unit in response to a trigger from an access and mobility management function. The access and mobility management function, a network slice selection function, or a combination thereof determines the configured network slice selection assistance information. The method includes providing the configured network slice selection assistance information to the remote unit via the access and mobility management function.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. Ser. No.17/180,038 filed on Feb. 19, 2021, which is a continuation applicationof U.S. Ser. No. 16/228,283 filed on Dec. 20, 2018, which claimspriority to U.S. Patent Application Ser. No. 62/609,642 entitled“PROVISIONING A MOBILE DEVICE WITH A NETWORK SLICING CONFIGURATION” andfiled on Dec. 22, 2017 for Genadi Velev, all of which are incorporatedherein by reference in their entirety.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to network slice selectionassistance information configuration.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), 5th Generation (“5G”),Positive-Acknowledgment (“ACK”), Access and Mobility Management Function(“AMF”), Access Point (“AP”), Binary Phase Shift Keying (“BPSK”), BaseStation (“BS”), Buffer Status Report (“BSR”), Bandwidth (“BW”),Bandwidth Part (“BWP”), Carrier Aggregation (“CA”), Contention-BasedRandom Access (“CBRA”), Clear Channel Assessment (“CCA”), Cyclic DelayDiversity (“CDD”), Code Division Multiple Access (“CDMA”), ControlElement (“CE”), Contention-Free Random Access (“CFRA”), Closed-Loop(“CL”), Coordinated Multipoint (“CoMP”), Cyclic Prefix (“CP”), CyclicalRedundancy Check (“CRC”), Channel State Information (“CSI”), CommonSearch Space (“CSS”), Control Resource Set (“CORESET”), Discrete FourierTransform Spread (“DFTS”), Downlink Control Information (“DCI”),Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data RadioBearer (“DRB”), Downlink Pilot Time Slot (“DwPTS”), Enhanced ClearChannel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), EvolvedNode B (“eNB”), Effective Isotropic Radiated Power (“EIRP”), EuropeanTelecommunications Standards Institute (“ETSI”), Frame Based Equipment(“FBE”), Frequency Division Duplex (“FDD”), Frequency DivisionMultiplexing (“FDM”), Frequency Division Multiple Access (“FDMA”),Frequency Division Orthogonal Cover Code (“FD-OCC”), 5G Node B or NextGeneration Node B (“gNB”), General Packet Radio Services (“GPRS”), GuardPeriod (“GP”), Global System for Mobile Communications (“GSM”), GloballyUnique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), HybridAutomatic Repeat Request (“HARQ”), Home Location Register (“HLR”), HomePLMN (“HPLMN”), Home Subscriber Server (“HSS”), Identity or Identifier(“ID”), Information Element (“IE”), International Mobile EquipmentIdentity (“IMEI”), International Mobile Subscriber Identity (“IMSI”),International Mobile Telecommunications (“IMT”), Internet-of-Things(“IoT”), Layer 2 (“L2”), Licensed Assisted Access (“LAA”), Load BasedEquipment (“LBE”), Listen-Before-Talk (“LBT”), Logical Channel (“LCH”),Logical Channel Prioritization (“LCP”), Long Term Evolution (“LTE”),Multiple Access (“MA”), Medium Access Control (“MAC”), MultimediaBroadcast Multicast Services (“MBMS”), Modulation Coding Scheme (“MCS”),Master Information Block (“MIB”), Multiple Input Multiple Output(“MIMO”), Mobility Management (“MM”), Mobility Management Entity(“MME”), Mobile Network Operator (“MNO”), massive MTC (“mMTC”), MaximumPower Reduction (“MPR”), Machine Type Communication (“MTC”), Multi UserShared Access (“MUSA”), Non Access Stratum (“NAS”), Narrowband (“NB”),Negative-Acknowledgment (“NACK”) or (“NAK”), Network Entity (“NE”),Network Function (“NF”), Non-Orthogonal Multiple Access (“NOMA”), NewRadio (“NR”), Network Repository Function (“NRF”), Network SliceInstance (“NSI”), Network Slice Selection Assistance Information(“NSSAI”), Network Slice Selection Function (“NSSF”), Network SliceSelection Policy (“NSSP”), Operation and Maintenance System (“OAM”),Orthogonal Frequency Division Multiplexing (“OFDM”), Open-Loop (“OL”),Other System Information (“OSI”), Power Angular Spectrum (“PAS”),Physical Broadcast Channel (“PBCH”), Power Control (“PC”), Primary Cell(“PCell”), Policy Control Function (“”PCF″), Physical Cell ID (“PCID”),Physical Downlink Control Channel (“PDCCH”), Packet Data ConvergenceProtocol (“PDCP”), Physical Downlink Shared Channel (“PDSCH”), PatternDivision Multiple Access (“PDMA”), Packet Data Unit (“PDU”), PhysicalHybrid ARQ Indicator Channel (“PHICH”), Power Headroom (“PH”), PowerHeadroom Report (“PHR”), Physical Layer (“PHY”), Public Land MobileNetwork (“PLMN”), Physical Random Access Channel (“PRACH”), PhysicalResource Block (“PRB”), Physical Uplink Control Channel (“PUCCH”),Physical Uplink Shared Channel (“PUSCH”), Quasi Co-Located (“QCL”),Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”),Registration Area (“RA”), Radio Access Network (“RAN”), Radio AccessTechnology (“RAT”), Random Access Procedure (“RACH”), Random AccessResponse (“RAR”), Radio Link Control (“RLC”), Radio Network TemporaryIdentifier (“RNTI”), Reference Signal (“RS”), Remaining Minimum SystemInformation (“RMSI”), Radio Resource Control (“RRC”), Resource SpreadMultiple Access (“RSMA”), Reference Signal Received Power (“RSRP”),Round Trip Time (“RTT”), Receive (“RX”), Sparse Code Multiple Access(“SCMA”), Scheduling Request (“SR”), Sounding Reference Signal (“SRS”),Single Carrier Frequency Division Multiple Access (“SC-FDMA”), SecondaryCell (“SCell”), Shared Channel (“SCH”), Sub-carrier Spacing (“SCS”),Service Data Unit (“SDU”), System Information Block (“SIB”), SubscriberIdentity/Identification Module (“SIM”),Signal-to-Interference-Plus-Noise Ratio (“SINR”), Service LevelAgreement (“SLA”), Session Management Function (“SMF”), Single NetworkSlice Selection Assistance Information (“S-NSSAI”), SynchronizationSignal (“SS”), Synchronization Signal Block (“SSB”), SupplementaryUplink (“SUL”), Subscriber Permanent Identifier (“SUPI”), Tracking Area(“TA”), TA Indicator (“TAI”), Transport Block (“TB”), Transport BlockSize (“TBS”), Time-Division Duplex (“TDD”), Time Division Multiplex(“TDM”), Time Division Orthogonal Cover Code (“TD-OCC”), TransmissionPower Control (“TPC”), Transmission Reception Point (“TRP”),Transmission Time Interval (“TTI”), Transmit (“TX”), Uplink ControlInformation (“UCI”), Unified Data Management Function (“UDM”), UnifiedData Repository (“UDR”), User Entity/Equipment (Mobile Terminal) (“UE”),Uplink (“UL”), Universal Mobile Telecommunications System (“UMTS”), UserPlane (“UP”), Uplink Pilot Time Slot (“UpPTS”), Ultra-reliability andLow-latency Communications (“URLLC”), UE Route Selection Policy(“URSP”), Visiting AMF (“vAMF”), Visiting NSSF (“vNSSF”), Visiting PLMN(“VPLMN”), and Worldwide Interoperability for Microwave Access(“WiMAX”).

In certain wireless communications networks, a network slicingconfiguration may be used. In such networks, a device may not know thenetwork slicing configuration to use.

BRIEF SUMMARY

Methods for NSSAI configuration are disclosed. Apparatuses and systemsalso perform the functions of the apparatus. One embodiment of a methodincludes determining a configured network slice selection assistanceinformation for a public land mobile network for a remote unit inresponse to a trigger from an access and mobility management function.In such an embodiment, the access and mobility management function, anetwork slice selection function, or a combination thereof determinesthe configured network slice selection assistance information. Incertain embodiments, the method includes providing the configurednetwork slice selection assistance information to the remote unit viathe access and mobility management function.

One apparatus for NSSAI configuration includes a processor thatdetermines a configured network slice selection assistance informationfor a public land mobile network for a remote unit in response to atrigger from an access and mobility management function. In such anembodiment, the access and mobility management function, a network sliceselection function, or a combination thereof determines the configurednetwork slice selection assistance information. In certain embodiments,the apparatus includes a transmitter that provides the configurednetwork slice selection assistance information to the remote unit viathe access and mobility management function.

One method for NSSAI configuration includes receiving, at a remote unit,a configured network slice selection assistance information for a publicland mobile network via an access and mobility management function. Insuch an embodiment, the access and mobility management function, anetwork slice selection function, or a combination thereof determinesthe configured network slice selection assistance information inresponse to a trigger from the access and mobility management function.

One apparatus for NSSAI configuration includes a receiver that receivesa configured network slice selection assistance information for a publicland mobile network via an access and mobility management function. Insuch an embodiment, the access and mobility management function, anetwork slice selection function, or a combination thereof determinesthe configured network slice selection assistance information inresponse to a trigger from the access and mobility management function.

One method for NSSAI configuration includes receiving, at a remote unit,first configured network slice selection assistance information for afirst public land mobile network. In some embodiments, the methodincludes storing, at the remote unit, the first configured network sliceselection assistance information for the first public land mobilenetwork. In certain embodiments, the method includes transmitting afirst acknowledgment in response to receiving the first configurednetwork slice selection assistance information. In such embodiments, thefirst acknowledgment indicates that the first configured network sliceselection assistance information was received. In various embodiments,the method includes receiving, at the remote unit, second configurednetwork slice selection assistance information for a second public landmobile network. In one embodiment, the method includes storing, at theremote unit, the second configured network slice selection assistanceinformation for the second public land mobile network. In someembodiments, the method includes transmitting a second acknowledgment inresponse to receiving the second configured network slice selectionassistance information. In such embodiments, the second acknowledgmentindicates that the second configured network slice selection assistanceinformation was received.

One apparatus for NSSAI configuration includes a receiver that receivesfirst configured network slice selection assistance information for afirst public land mobile network. In some embodiments, the apparatusincludes a processor that stores the first configured network sliceselection assistance information for the first public land mobilenetwork. In certain embodiments, the apparatus includes a transmitterthat transmits a first acknowledgment in response to receiving the firstconfigured network slice selection assistance information. In suchembodiments, the first acknowledgment indicates that the firstconfigured network slice selection assistance information was received.In various embodiments, the receiver receives second configured networkslice selection assistance information for a second public land mobilenetwork; the processor stores the second configured network sliceselection assistance information for the second public land mobilenetwork; and the transmitter transmits a second acknowledgment inresponse to receiving the second configured network slice selectionassistance information. In such embodiments, the second acknowledgmentindicates that the second configured network slice selection assistanceinformation was received.

One method for NSSAI configuration includes determining, within aunified data management function, a default network slice selectionassistance information for a public land mobile network for a remoteunit. In some embodiments, the method includes providing the defaultnetwork slice selection assistance information to the remote unit.

One apparatus for NSSAI configuration includes a processor thatdetermines, within a unified data management function, a default networkslice selection assistance information for a public land mobile networkfor a remote unit. In various embodiments, the apparatus includes atransmitter that provides the default network slice selection assistanceinformation to the remote unit.

One method for NSSAI configuration includes receiving, at a remote unit,a default network slice selection assistance information for a publicland mobile network. In such an embodiment, a unified data managementfunction determines the default network slice selection assistanceinformation and provides the default network slice selection assistanceinformation to the remote unit.

One apparatus for NSSAI configuration includes a receiver that receivesa default network slice selection assistance information for a publicland mobile network. In such an embodiment, a unified data managementfunction determines the default network slice selection assistanceinformation and provides the default network slice selection assistanceinformation to the apparatus.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for NSSAI configuration;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for NSSAI configuration;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for NSSAI configuration;

FIG. 4 is a schematic block diagram illustrating one embodiment ofcommunications for default UE provisioning with a configured NSSAI;

FIG. 5 is a schematic block diagram illustrating one embodiment ofcommunications for a subscription information change in a UDM/UDR and UEnetwork slicing configuration;

FIG. 6 is a schematic block diagram illustrating one embodiment ofcommunications for signaling flow to provision a UE with a sliceconfiguration in a roaming configuration;

FIG. 7 is a schematic block diagram illustrating one embodiment ofcommunications for signaling flow to provision a UE with a sliceconfiguration via a PCF;

FIG. 8 is a flow chart diagram illustrating one embodiment of a methodfor NSSAI configuration;

FIG. 9 is a flow chart diagram illustrating another embodiment of amethod for NSSAI configuration;

FIG. 10 is a flow chart diagram illustrating a further embodiment of amethod for NSSAI configuration;

FIG. 11 is a flow chart diagram illustrating yet another embodiment of amethod for NSSAI configuration;

FIG. 12 is a flow chart diagram illustrating a yet further embodiment ofa method for NSSAI configuration.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 forNSSAI configuration. In one embodiment, the wireless communicationsystem 100 includes remote units 102 and network units 104. Even thougha specific number of remote units 102 and network units 104 are depictedin FIG. 1 , one of skill in the art will recognize that any number ofremote units 102 and network units 104 may be included in the wirelesscommunication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), aerialvehicles, drones, or the like. In some embodiments, the remote units 102include wearable devices, such as smart watches, fitness bands, opticalhead-mounted displays, or the like. Moreover, the remote units 102 maybe referred to as subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, UE,user terminals, a device, or by other terminology used in the art. Theremote units 102 may communicate directly with one or more of thenetwork units 104 via UL communication signals.

The network units 104 may be distributed over a geographic region. Incertain embodiments, a network unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, a core network, anaerial server, a radio access node, an AP, NR, a network entity, an AMF,a UDM, a UDR, a UDM/UDR, a PCF, a RAN, an NSSF, or by any otherterminology used in the art. The network units 104 are generally part ofa radio access network that includes one or more controllerscommunicably coupled to one or more corresponding network units 104. Theradio access network is generally communicably coupled to one or morecore networks, which may be coupled to other networks, like the Internetand public switched telephone networks, among other networks. These andother elements of radio access and core networks are not illustrated butare well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with NR protocols standardized in 3GPP, wherein the networkunit 104 transmits using an OFDM modulation scheme on the DL and theremote units 102 transmit on the UL using a SC-FDMA scheme or an OFDMscheme. More generally, however, the wireless communication system 100may implement some other open or proprietary communication protocol, forexample, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants,CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. Thepresent disclosure is not intended to be limited to the implementationof any particular wireless communication system architecture orprotocol.

The network units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The network units 104 transmit DL communicationsignals to serve the remote units 102 in the time, frequency, and/orspatial domain.

In one embodiment, a remote unit 102 may receive a configured networkslice selection assistance information for a public land mobile networkvia an access and mobility management function. In such an embodiment,the access and mobility management function, a network slice selectionfunction, or a combination thereof determines the configured networkslice selection assistance information in response to a trigger from theaccess and mobility management function. Accordingly, the remote unit102 may be used for NSSAI configuration.

In certain embodiments, a network unit 104 may determine a configurednetwork slice selection assistance information for a public land mobilenetwork for a remote unit 102 in response to a trigger from an accessand mobility management function. In such an embodiment, the access andmobility management function, a network slice selection function, or acombination thereof determines the configured network slice selectionassistance information. In certain embodiments, the network unit 104 mayprovide the configured network slice selection assistance information tothe remote unit 102 via the access and mobility management function.Accordingly, the network unit 104 may be used for NSSAI configuration.

In one embodiment, a remote unit 102 may receive first configurednetwork slice selection assistance information for a first public landmobile network. In some embodiments, the remote unit 102 may store thefirst configured network slice selection assistance information for thefirst public land mobile network. In certain embodiments, the remoteunit 102 may transmit a first acknowledgment in response to receivingthe first configured network slice selection assistance information. Insuch embodiments, the first acknowledgment indicates that the firstconfigured network slice selection assistance information was received.In various embodiments, the remote unit 102 may receive secondconfigured network slice selection assistance information for a secondpublic land mobile network. In one embodiment, the remote unit 102 maystore the second configured network slice selection assistanceinformation for the second public land mobile network. In someembodiments, the remote unit 102 may transmit a second acknowledgment inresponse to receiving the second configured network slice selectionassistance information. In such embodiments, the second acknowledgmentindicates that the second configured network slice selection assistanceinformation was received. Accordingly, the remote unit 102 may be usedfor NSSAI configuration.

In certain embodiments, a network unit 104 may determine, within aunified data management function, a default network slice selectionassistance information for a public land mobile network for a remoteunit 102. In some embodiments, the network unit 104 may provide thedefault network slice selection assistance information to the remoteunit 102. Accordingly, the network unit 104 may be used for NSSAIconfiguration.

In one embodiment, a remote unit 102 may receive a default network sliceselection assistance information for a public land mobile network. Insuch an embodiment, a unified data management function determines thedefault network slice selection assistance information and provides thedefault network slice selection assistance information to the remoteunit 102. Accordingly, the remote unit 102 may be used for NSSAIconfiguration.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used forNSSAI configuration. The apparatus 200 includes one embodiment of theremote unit 102. Furthermore, the remote unit 102 may include aprocessor 202, a memory 204, an input device 206, a display 208, atransmitter 210, and a receiver 212. In some embodiments, the inputdevice 206 and the display 208 are combined into a single device, suchas a touchscreen. In certain embodiments, the remote unit 102 may notinclude any input device 206 and/or display 208. In various embodiments,the remote unit 102 may include one or more of the processor 202, thememory 204, the transmitter 210, and the receiver 212, and may notinclude the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Invarious embodiments, the processor 202 may: store a first configurednetwork slice selection assistance information for a first public landmobile network; and store a second configured network slice selectionassistance information for the second public land mobile network. Theprocessor 202 is communicatively coupled to the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thenetwork unit 104 and the receiver 212 is used to receive DLcommunication signals from the network unit 104, as described herein. Insome embodiments, the receiver 212 receives a configured network sliceselection assistance information for a public land mobile network via anaccess and mobility management function. In such an embodiment, theaccess and mobility management function, a network slice selectionfunction, or a combination thereof determines the configured networkslice selection assistance information in response to a trigger from theaccess and mobility management function.

In some embodiments, the receiver 212 receives first configured networkslice selection assistance information for a first public land mobilenetwork. In certain embodiments, the transmitter 210 transmits a firstacknowledgment in response to receiving the first configured networkslice selection assistance information. In such embodiments, the firstacknowledgment indicates that the first configured network sliceselection assistance information was received. In various embodiments,the receiver 212 receives second configured network slice selectionassistance information for a second public land mobile network. In someembodiments, the transmitter 210 transmits a second acknowledgment inresponse to receiving the second configured network slice selectionassistance information. In such embodiments, the second acknowledgmentindicates that the second configured network slice selection assistanceinformation was received.

In various embodiments, the receiver 212 receives a default networkslice selection assistance information for a public land mobile network.In such an embodiment, a unified data management function determines thedefault network slice selection assistance information and provides thedefault network slice selection assistance information to the remoteunit 102.

Although only one transmitter 210 and one receiver 212 are illustrated,the remote unit 102 may have any suitable number of transmitters 210 andreceivers 212. The transmitter 210 and the receiver 212 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 210 and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used forNSSAI configuration. The apparatus 300 includes one embodiment of thenetwork unit 104. Furthermore, the network unit 104 may include aprocessor 302, a memory 304, an input device 306, a display 308, atransmitter 310, and a receiver 312. As may be appreciated, theprocessor 302, the memory 304, the input device 306, the display 308,the transmitter 310, and the receiver 312 may be substantially similarto the processor 202, the memory 204, the input device 206, the display208, the transmitter 210, and the receiver 212 of the remote unit 102,respectively.

In various embodiments, the processor 302 determines a configurednetwork slice selection assistance information for a public land mobilenetwork for a remote unit 102 in response to a trigger from an accessand mobility management function. In such an embodiment, the access andmobility management function, a network slice selection function, or acombination thereof determines the configured network slice selectionassistance information. In certain embodiments, the transmitter 310provides the configured network slice selection assistance informationto the remote unit 102 via the access and mobility management function.

In some embodiments, the processor 302 determines, within a unified datamanagement function, a default network slice selection assistanceinformation for a public land mobile network for a remote unit 102. Invarious embodiments, the transmitter 310 provides the default networkslice selection assistance information to the remote unit 102.

Although only one transmitter 310 and one receiver 312 are illustrated,the network unit 104 may have any suitable number of transmitters 310and receivers 312. The transmitter 310 and the receiver 312 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 310 and the receiver 312 may be part of a transceiver.

In some embodiments, a network may be partitioned into one or morenetwork slices and a mobile network operator may configure the one ormore network slices to serve one or more particular services or serviceproviders. A UE may be subscribed to services served by multiple networkslices.

One example of a network slice configuration for a UE is as follows:

Configured NSSAI for HPLMN: [S-NSSAI-1, S-NSSAI-2, S-NSSAI-3]

Configured NSSAI for VPLMN-1: [S-NSSAI-1, S-NSSAI-4]

Mapping [S-NSSAI-4 ==S-NSSAI-2, S-NSSAI-3]

Configured NSSAI for VPLMN-2: [S-NSSAI-5, S-NSSAI-6]

Mapping [S-NSSAI-5 ==S-NSSAI-1]

Mapping [S-NSSAI-6 ==S-NSSAI-2, S-NSSAI-3]

It should be noted that this example is for a configured NSSAI, forallowed NSSAI there may be independent IEs signaled to the UE in aregistration accept message.

As used herein, “network slice configuration,” “network slicingconfiguration,” and/or “slice configuration information” may mean that aUE is provided with: a configured NSSAI for a HPLMN; and/or one or moreconfigured NSSAIs for other PLMNs associated with mapping of eachS-NSSAI of the configured NSSAI to the HPLMN S-NSSAI values. In someembodiments, a UE provisioning performed by a HPLMN is referred to as adefault UE network slice configuration and may contain configured NSSAIfor the HPLMN and one or more default configured NSSAIs for other PLMNs.Any other serving PLMN (e.g., VPLMN) may provide additional networkslice configurations to the UE (e.g. configured NSSAI for a servingPLMN) only applicable to the serving PLMN.

As used herein, “subscription information” may mean subscription datawhich may contain one or more parameters stored in a UDR. In someembodiments, subscription information may include policy data and/orstructured data for internal exposure and/or external exposure. Thesubscription information may be downloaded in a UDM, and the UDM maysend the subscription information to other NFs such as AMF, SMF, and soforth. Therefore, the term UDM/UDR may be used to refer to the combinedfunctions of the UDR and the UDM.

In certain embodiments, if a UE does not have a configured NSSAI for aparticular serving PLMN, the UE may not send a requested NSSAI in aregistration request message (e.g., with an initial registration). Aftera serving AMF authenticates the UE and downloads the UE's subscriptioninformation from the UDM, the serving AMF knows the subscribed S-NSSAIsfor this UE. If there are more than one subscribed S-NSSAIs, it may bebeneficial to perform UE slice configuration in the UE (e.g., providingthe UE with a configured NSSAI).

In various embodiments, not including a requested NSSAI is an indicationto a serving AMF that a UE does not have a configured NSSAI for a PLMNto which the UE is attempting registration.

In some embodiments, an NSSF is an entity (e.g., NF) in a 5G system thathas overview about slice configuration in an entire PLMN. In suchembodiments, the NSSF may support the following functionality: selectinga set of network slice instances to serve a UE; determining an allowedNSSAI and, if needed, a mapping to subscribed S-NSSAIs; and/ordetermining an AMF set to be used to serve the UE, or, based onconfiguration, a list of candidate AMFs (e.g., by querying the NRF);and/or determining the NRF to be used for a particular network sliceinstance.

In certain embodiments, UE subscription information in a UDM/UDR keepstrack (e.g., using a flag and/or a parameter) of whether a UE has beenprovisioned with a configured NSSAI for a HPLMN and/or one or moreconfigured NSSAIs for VPLMNs. If the UDM/UDR uses a flag and/or aparameter, the flag and/or the parameter may be configured and/orupdated as follows: 1) after the UE has been successfully provided oneor more configured NSSAIs by an AMF, the AMF may update the UDM/UDR withinformation indicating that the one or more configured NSSAIs for theHPLMN and/or VPLMNs has been provided; and/or 2) the UDM/UDR may create,store, and/or signal to the AMF (e.g., within a subscription retrievalor within a separate procedure) subscribed S-NSSAI for the HPLMN and/orconfigured NSSAIs for one or more VPLMNs.

In various embodiments, if subscribed S-NSSAIs in a UDM/UDR change, theUDM/UDR may trigger a subscription information update procedure thatincludes transmitting a message to a serving AMF (e.g., if the servingAMF is registered at the UDM/UDR) and may request a UE network slicingconfiguration update. In such embodiments, the UDM/UDR may indicate tothe serving AMF at least one of the following: 1) an indication that aconfigured NSSAI for a HPLMN is no longer valid (in such a case, the AMFmay construct a new configured NSSAI for the HPLMN based on a list ofsubscribed S-NSSAIs); and/or 2) a new subscribed S-NSSAI for the HPLMNand/or one or more configured NSSAIs for one or more VPLMNs. In suchembodiments, the AMF may update a UE network slicing configuration usinga UE configuration update procedure.

In some embodiments, if a requested NSSAI is not included (or is equalto zero) in a registration request message, then: 1) in a non-roamingconfiguration, if a configured S-NSSAI for a HPLMN is not received froma UDM/UDR, an AMF determines that a UE should be provided with a networkslicing configuration and the AMF derives a configured NSSAI for theHPLMN based on subscribed NSSAIs (e.g., the configured NSSAI for theHPLMN contains a full list of subscribed NSSAIs)—the configured NSSAIfor the HPLMN may also include an indication for default S-NSSAIs and/orthe S-NSSAIs may be in priority order; 2) in a roaming configuration,the AMF may determine that either there is no configured NSSAI or thatthe configured NSSAI needs to be updated for a serving PLMN, therefore,the AMF either (1) creates and/or derives a new configured NSSAI for theserving PLMN by itself or (2) request the NSSF to derive a configuredNSSAI for this UE.

In certain embodiments, if a requested NSSAI is included in aregistration request message but one or more of S-NSSAI values are notknown to an AMF, the AMF may request information from an NSSF aboutresolution and the AMF (together with NSSF) may determine that aconfigured NSSAI for the PLMN is not correct and needs to be updated.

In various embodiments, an NSSF may determine a configured NSSAI for aUE and mapping of the configured NSSAI for a HPLMN. In such embodiments,the NSSF may not need to derive the configured NSSAI every time if anAMF requests an NSSAI from the NSSF (e.g., request for allowed NSSAI,request for the configured NSSAI); however, the AMF may include an extraindication that indicates whether the NSSF is to derive the configuredNSSAI. In such embodiments, the indication to the NSSF may include:subscribed S-NSSAIs; a PLMN ID of a SUPI, a request from the AMF toderive the configured NSSAI, a request from the AMF for allowed NSSAI,and/or a request from the AMF for the configured NSSAI for the HPLMN.

In one embodiment, a UE may be provided and/or updated with a networkslicing configuration for a HPLMN (e.g., provided a configured NSSAI forthe HPLMN). In such an embodiment, an AMF may determine whether toprovide and/or update the UE network slicing configuration. In certainembodiments, a UDM/UDR provides new information (e.g., parameters,indications) to an AMF to assist in updating the UE network slicingconfiguration. In some embodiments, after successful UE configuration,an AMF may update a UDM/UDR with a message (e.g., ‘UE Provisioned withConfigured NSSAI for the HPLMN’) after the UE has been successfullyprovided a configured NSSAI for a HPLMN.

In various embodiments, providing and/or updating a UE with a networkslicing configuration for a HPLMN may be referred to as a default UEnetwork slice configuration. In such embodiments, the default networkslice configuration contains at least a configured NSSAI for the HPLMNand may contain other configured NSSAI which may apply either to onePLMN or to all PLMNs that do not have a specific configured NSSAI. Insome embodiments, such as in non-roaming configurations, an AMF maycreate a configured NSSAI based on subscribed S-NSSAIs as received froma UDM. In various embodiments, a HPLMN may provide a UE with configuredNSSAI for other PLMNs.

In certain embodiments, because an AMF may not know to which other PLMNa specific configured NSSAI can apply, a UDM/UDR may indicate thisinformation (e.g., a default configured NSSAI for any VPLMN) to the AMF.

In some embodiments, such as in a roaming configuration, if a change toany subscribed S-NSSAIs for a UE occurs in a UDM/UDR, then a servingvAMF and/or vNSSF may update a configured NSSAI for a VPLMN, but theServing vAMF may not be able to update the configured NSSAI for a HPLMN(e.g., because the vAMF may not have a complete list of subscribedS-NSSAIs). Therefore, in a roaming configuration, a UDM/UDR may send a“Configured NSSAI for the HPLMN” as a transparent container to a vAMFand the vAMF may perform a UE configuration update procedure to updatethe ‘Configured NSSAI for the HPLMN’ for the UE together with the‘Configured NSSAI for the VPLMN’.

For example, a UDM/UDR may create and/or store the following networkslice configuration information which may be stored in the UE'ssubscription information:

Configured NSSAI for HPLMN: [S-NSSAI-1, S-NSSAI-2, S-NSSAI-3]

(Default) Configured NSSAI for any VPLMN: [S-NSSAI-1, S-NSSAI-4]

Mapping [S-NSSAI-4 ==S-NSSAI-2]

In certain embodiments, in a non-roaming configuration, a UDM/UDR maysend a configured NSSAI for any VPLMN (e.g., a default configured NSSAIfor any VPLMN) and/or may send a list of PLMNs to which the configuredNSSAI for a HPLMN applies. In such embodiments, the configured NSSAI forthe HPLMN may be created at the AMF. In various embodiments, such as ina roaming configuration, a UDM/UDR may send a configured NSSAI for aHPLMN and/or a default configured NSSAI for any VPLMN as one or moretransparent containers to a vAMF.

FIG. 4 is a schematic block diagram illustrating one embodiment ofcommunications 400 for default UE provisioning with a configured NSSAI.The communications 400 includes messages transmitted between a UE 402, aRAN 404, a serving AMF 406, an NSSF 408, and a UDM/UDR 410. As may beappreciated, each communication described herein may include one or moremessages.

In a first communication 412 transmitted from the UE 402 to the RAN 404,the UE 402 may send a NAS registration request message to the RAN 404that may include: a UE ID (e.g., SUPI); a registration type (e.g.,initial, mobility), and/or a requested NSSAI. The NAS registrationrequest message may be encapsulated in RRC signaling. In someembodiments, the RRC signaling contains a requested NSSAI.

In a second communication 414 transmitted from the RAN 404 to theserving AMF 406, the RAN 404 may send the NAS registration requestmessage to the serving AMF 406. There may be multiple ways for theserving AMF 406 to determine whether the UE 402 is provided with aconfigured NSSAI for a serving PLMN: 1) if a requested NSSAI is notincluded (or empty) in the NAS registration request message, then thismay be an implicit indication to the serving AMF 406 that the UE 402does not have a configured NSSAI for the serving PLMN; 2) the UE 402 mayinclude an explicit indication in the NAS registration request messagethat there is no configured NSSAI for the serving PLMN (the UE 402 maydetermine that there is no configured NSSAI based on an internallystored slice configuration and a PLMN ID to which the UE 402 isattempting to register and/or attach. If there is no stored configuredNSSAI for the PLMN ID, then the UE 402 determines that there is noconfigured NSSAI for the serving PLMN and includes the indication in theNAS registration request message. For example, the UE 402 may include a‘Configured NS SAI availability’ indication); and/or 3) based on anexplicit indication from a UDM/UDR (as described in a fourthcommunication 418).

In a third communication 416 transmitted from the serving AMF 406 to theUDM/UDR 410, the serving AMF 406 may request the UE subscriptioninformation from the UDM/UDR 410 via a UE subscription request. Forexample, the serving AMF 406 may register with the UDM/UDR 410 using aNudm_UECM_Registration service.

In the fourth communication 418 transmitted from the UDM/UDR 410 to theserving AMF 406, the serving AMF 406 may retrieve access and mobilitysubscription data and SMF selection subscription data using a serviceNudm_SDM_Get, for example. The information of the fourth communication418 may be sent either in a subscription response message or in aseparate message from the UDM/UDR 410 to the serving AMF 406 (e.g., amessage specific for UE configuration information). The information ofthe fourth communication 418 may include:

1) an indication and/or parameter about whether a configured NSSAI for aHPLMN has been provided to the UE 402. For example, this indicationand/or parameter may be called ‘Configured NSSAI for HPLMN’ or any othername expressing the same or a similar meaning. For example, this can bean IE having different values (e.g., ‘Configured NSSAI for HPLMNProvisioned’=TRUE (or FALSE)). In an initial registration procedure ofthe UE 402 in a PLMN, it may be assumed that the UE 402 is notconfigured with any slicing information (e.g., no configured NSSAI forthe HPLMN). In this case, the indication may be ‘Configured NSSAI forHPLMN Provisioned’=FALSE (i.e., the serving AMF 406 learns that the UE402 has no configured NSSAI for the HPLMN). In some embodiments, theindication and/or parameter may be sent only to AMFs in a VPLMN(assuming that the AMF in the HPLMN can create the configured NSSAI forthe HPLMN based on the list of subscribed S-NSSAIs);

2) a list of one or more configured NASSAIs for one or more PLMNs (e.g.,that the UDM/UDR 410 derives and/or stores) For example, the UDM/UDR 410may send a list such as: configured NSSAI for HPLMN; configured NSSAIfor VPLMN1; configured NSSAI for VPLMN2; and so forth. The UDM/UDR 410may be able to know a configured NSSAI for VPLMN1 and/or VPLMN2 based onSLAs between the PLMNs. In addition, the UDM/UDR 410 may send a mappingof configured NSSAI per VPLMN (e.g., containing a mapping of theconfigured NSSAI from the serving PLMN to the configured NSSAI for theHPLMN). One particular example of what information the UDM/UDR 410 maysignal to the serving AMF 406 network slicing configuration information(or configured NSSAIs for PLMNs) is described in relation to element 430below;

3) an indication of whether an NSSP has been provisioned in the UE 402.For example, this indication may be called ‘NSSP provisioned in the UE’indication or any other name expressing same or similar meaning. Thisindication may be set (e.g., set to TRUE, set to “1”) if the UE 402 hasalready been provided with URSP containing NSSP; and/or

4) a device ID and/or equipment ID (e.g., IMEI) to indicate to theserving AMF 406 for which device IDs the network slicing configuration(e.g., configured NSSAI for HPLMN, VPLMN, and/or NSSP) has been alreadyperformed.

The information signaled from the UDM/UDR 410 to the serving AMF 406described herein may be optionally included depending on the UDM/UDR 410configuration (or on MNO preferences, network policies, and/or networkconfiguration). Moreover, without the information from the UDM/UDR 410,the serving AMF 406 may decide that network slicing configuration (e.g.,configured NSSAI for the HPLMN) is to be provisioned in the UE 402 basedon that (1) the UE 402 has not included a requested NSSAI in theregistration request message and (2) there are at least one or moresubscribed S-NSSAIs in the UE subscription information.

The UDM/UDR 410 may also indicate to the serving AMF 406 (e.g., in theHPLMN) a list of PLMN IDs to which subscribed S-NSSAIs are applicable.This indication may be called, for example, ‘Applicability of SubscribedS-NSSAIs to PLMN(s)’. This indication may also indicate ‘all PLMNs’ forwhich no other configured NSSAI is provided, in which case theconfigured NSSAI may be a default configured NSSAI for any VPLMN. Thisindication may enable the serving AMF 406 to indicate to the UE 402 towhich other PLMNs, besides the HPLMN, the configured NSSAI for the HPLMNis applicable.

In a fifth communication 420 between the UE 402, the RAN 404, theserving AMF 406, the NSSF 408, and/or the UDM/UDR 410, messages may besent based on the registration procedure as described in TS 23.502.

In a sixth communication 422 transmitted from the serving AMF 406 to theUE 402, the serving AMF 406 may provide the UE 402 with the configuredNSSAI for the HPLMN. In some embodiments, the serving AMF 406 may createan IE called configured NSSAI which includes all subscribed S-NSSAIsobtained from the UDM/UDR 410 via the third communication 416 and thefourth communication 418.

The serving AMF 406 may determine 424 whether to provide the configuredNSSAI for HPLMN based on at least one of the following conditions:

1) the serving AMF 406 may take into consideration information aboutwhether the UE 406 is provided with configured NSSAI for a current PLMN(e.g., HPLMN). The serving AMF 406 may receive this information from NFssuch as a PCF. If the information is negative (e.g., meaning that the UE402 hasn't been provided the configured NSSAI for HPLMN), then theserving AMF 406 may decide to provide the configured NSSAI for HPLMN viacommunications 428 through 438. If the information is positive (e.g.,meaning that the UE 402 has been provided the configured NSSAI forHPLMN), then the serving AMF 406 may decide to omit communications 428through 438;

2) the serving AMF 406 may take into consideration information aboutwhether the UE 406 is provided with NSSP. The serving AMF 406 mayreceive this information from NFs such as a PCF. If this information isnegative (e.g., meaning that the UE 402 hasn't been provided with NSSP),then the serving AMF 406 may decide to provide the UE 402 with theconfigured NSSAI. In some embodiments, the configured NSSAI contains asingle S-NSSAI value which may be a default S-NSSAI from the list ofsubscribed S-NSSAIs. The serving AMF 406 may then perform communications428 through 438. If the information is positive (e.g., meaning that theUE 402 has been provided with NSSP), then the serving AMF 406 may decideto provide the UE with the configured NSSAI. In various embodiments, theconfigured NSSAI contains a full list of subscribed S-NSSAIs. Theserving AMF 406 may then perform communications 428 through 438;

3) the serving AMF 406 may take into consideration a device ID and/or anequipment ID corresponding to providing the configured NSSAI to the UE402. If the serving AMF 406 determines that a current device ID isdifferent from the device ID as received in the fourth communication418, then the serving AMF 406 may decide to provide the configured NSSAIto the UE 402 and perform communications 428 through 438. If the servingAMF 406 determines that the current device ID is the same as the deviceID as received in the fourth communication 418 and the UE 402 has beenalready provided with the configured NSAAI, then the serving AMF 406 maydecide to omit communications 428 through 438; and/or

4) if the serving AMF 406 receives configured NSSAI for other PLMNs inthe fourth communication 418, the serving AMF 406 may not modify IEs(e.g., they are handled like a transparent container). Because theUDM/UDR 410 may not know slice specific SLAs with corresponding roamingpartners, but the NSSF 408 may know such information, in a possibleseventh communication 426 between the serving AMF 406 and the NSSF 408,the serving AMF 406 may enquire the NSSF 408 about received ‘ConfiguredNSSAI for other PLMN(s)’ information in order to obtain mappinginformation of the configured NSSAI for other PLMNs to the configuredNSSAI for HPLMN. The serving AMF 406 may include the information asreceived from the UDM/UDR 410 in the communication 428.

In an eighth communication 428 from the serving AMF 406 to the UE 402,the serving AMF 406 initiates a UE configuration update procedure toconfigure the UE 402 with configured NSSAI for the HPLMN and otherPLMNs. Specifically, the serving AMF 406 may send a UE configurationupdate command message. The configured NSSAI IE may contain multiplefields (e.g., multiple S-NSSAI values and additional PLMN IDs for whichthe Configured NSSAI applies). The configured NSSAI IE may contain alist of S-NSSAIs in priority order (e.g., the first occurring S-NSSAImay be used in the requested NSSAI if there is no NSSP configured in theUE 402).

The UE 402 may store 430 the network slicing configuration information(e.g., configured NSSAIs and/or applicable PLMN IDs) in non-volatilememory. One example of how this information may be stored is as follows:

Configured NSSAI for HPLMN: [S-NSSAI-1, S-NSSAI-2, S-NSSAI-3]

(Default) Configured NSSAI for any VPLMN: [S-NSSAI-1, S-NSSAI-4]

Mapping [S-NSSAI-4==S-NSSAI-2]

In this example, the S-NSSAI-1, the S-NSSAI-2, and the S-NSSAI-3 may bevalues used in the HPLMN, whereas the values S-NSSAI-2 and S-NSSAI-3 maybe PLMN-specific values. The S-NSSAI-1 may be a default S-NSSAI. Theconfigured NSSAI for any VPLMN may be used by the UE 402 for any VPLMNwhich does not provide explicit new configured NSSAI. In this examplethe S-NSSAI-4 is a standardized value that maps to the PLMN-specificvalues S-NSSAI-2 and S-NSSAI-3. In this example, it is assumed that theUE's NSSP may include all values S-NSSAI-1, S-NSSAI-2, S-NSSAI-3. Someapplications may map to S-NSSAI-3 as a higher priority mapping andS-NSSAI-1 as a lower priority mapping (e.g., if S-NSSAI-3 is not part ofallowed NSSAI). Moreover, the mapping information (e.g.,S-NSSAI-4==S-NSSAI-2) may originate from the NSSF.

In a possible ninth communication 432 from the UE 402 to the serving AMF406, the UE 402 may respond to the eighth communication 428 with a UEconfiguration update complete message to confirm the reception andsuccessful network slicing configuration in the UE 402.

The serving AMF 406 may update 434 its information to indicate that theUE 402 has been provided the configured NSSAI.

In a tenth communication 436 from the serving AMF 406 to the UDM/UDR410, the serving AMF 406 may initiate a procedure to perform a UEsubscription information update to inform the UDM/UDR 410 that the UE402 has been provided the configured NSSAI for the HPLMN. The servingAMF 406 may inform the UDM/UDR 410 about whether the whole list ofsubscribed S-NSSAIs has been provided to the UE 402, or whether only asingle default S-NSSAI value has been provided to the UE 402. Inaddition, the serving AMF 406 may include a device ID and/or anequipment ID (e.g. IMEI), so that the UDM/UDR 410 knows and stores thedevice ID and/or the equipment ID to which the configured NSSAI has beenprovided. Accordingly, the device ID and/or the equipment ID may be usedby the UDM/UDR 410 to determine whether a new device is used with thesame subscription profile (e.g., with the same SIM card). The UDM/UDR410 can either create a new entry for providing the configured NSSAI toa device having the device ID, or update an existing entry for thedevice ID.

The UDM/UDR 410 may update 438 the UE subscription information using theinformation received from the serving AMF 406. For example, afterreceiving the information received from the serving AMF 406 in the tenthcommunication 436, the UDM/UDR 410 updates the status of the IE‘Configured NSSAI for HPLMN Provisioned’=from FALSE to TRUE. Inaddition, the UDM/UDR 410 may store the device ID (e.g., IMEI) for whichthe configured NSSAI has been provided.

To summarize some aspects relating to FIG. 4 , there are several optionsfor deriving and/or creating the configured NSSAI for the HPLMN: (1) itcan be derived in the serving AMF 406 in the HPLMN; or (2) it can bederived and/or stored in the UDM/UDR 410 and sent to the serving AMF406. For configured NSSAIs for other PLMNs (e.g., VPLMNs), theinformation may be created at the UDM/UDR 410 and sent to the servingAMF 406 to be provided to the UE 402. The UDM/UDR 410 keeps track ofwhether the UE 402 has been provided configured NSSAIs.

In one embodiment, a UE may be provided with an updated sliceconfiguration (e.g., configured NSSAI for a serving VPLMN) ifsubscription information in a UDM/UDR changes, in particular ifsubscribed S-NSSAIs change. FIG. 5 shows this embodiment (e.g., changingsubscribed S-NSSAIs in the UDM/UDR), updating an AMF, and updating theconfiguration (e.g., configured NSSAI for the HPLMN) in a UE.

In certain embodiments, such as in a roaming configuration, if there isa change to any subscribed S-NSSAIs for a UE that occurs in a UDM/UDR,then a serving vAMF and/or vNSSF may update the configured NSSAI for theVPLMN, but the serving vAMF may not be able to update the configuredNSSAI for the HPLMN. In some embodiments, a UDM/UDR may send aconfigured NSSAI for a HPLMN as a transparent container to a vAMF andthe vAMF may perform a UE configuration update procedure to update the‘Configured NSSAI for the HPLMN’ for the UE together with the‘Configured NS SAI for the VPLMN’.

FIG. 5 is a schematic block diagram illustrating one embodiment ofcommunications 500 for a subscription information change in a UDM/UDRand UE network slicing configuration. The communications 500 includesmessages transmitted between a UE 502, a RAN 504, a serving AMF 506, anNSSF 508, and a UDM/UDR 510. As may be appreciated, each communicationdescribed herein may include one or more messages.

A UE's subscription information in the UDM/UDR 510 may change 512 at anytime. For example, if the list of subscribed S-NSSAIs changes (e.g.,adding or removing S-NSSAI values), then this may have an impact on theUE's configuration and also may impact the UE 502 current registration.The UDM/UDR 510 may trigger a subscription update procedure.

In a first communication 514 from the UDM/UDR 510 to the serving AMF506, the UDM/UDR 510 may initiate a subscription information updatedprocedure transmitted to the serving AMF 506. For example, the UDM/UDR510 may invoke a Nudm_SDM_Notification service provided to the servingAMF 506 subscribed for notifications. Depending on whether the UE 502 isregistered in the HPLMN or in a VPLMN, the following may occur: 1) ifthe UE 502 is registered in the HPLMN (e.g., the serving AMF 506 is inthe HPLMN), the UDM/UDR 510 includes in signaling to the serving AMF 506at least one of the following: a SUPI; new subscribed S-NSSAIs;configured NSSAI for HPLMN indication; NSSP provisioned in the UEindication; a list of PLMN IDs; and/or MEI; 2) if the UE 502 isregistered in a VPLMN (e.g., the Serving AMF 506 is in VPLMN, calledvAMF), the UDM/UDR 510 includes in signaling to the serving AMF 506 atleast one of the following: a SUPI; new subscribed S-NSSAIs; configuredNSSAI for HPLMN; configured NSSAIs for other PLMNs; and/or IMEI. In someembodiments, information about the configured NSSAI for HPLMN and theconfigured NSSAIs for other PLMNs may be included in a containertransparent to the vAMF containing a list of S-NSSAIs that may beprovided to the UE 506 from the vAMF; however, the vAMF may not changethe content of the transparent container.

The serving AMF 506 behaves 516 based on the first communication 514,depending whether the serving AMF 506 is a hAMF (e.g., in HPLMN) or vAMF(e.g., in VPLMN). If the serving AMF 506 is located in the VPLMN, theserving AMF 506, based on an updated subscribed S-NSSAIs and/or the newconfigured NSSAI for the HPLMN, may create and/or derive the configuredNSSAI for the VPLMN and a corresponding mapping of configured NSSAIinformation. The serving AMF 506 either derives the configured NSSAI andmapping of configured NSSAI by itself or together with the NSSF.

In a second communication 518 from the serving AMF 506 to the UE 502,the serving AMF 506 initiates a UE configuration update procedure toconfigure the UE 502 with configured NSSAI for the HPLMN and otherPLMNs. Specifically, the serving AMF 506 may send a UE configurationupdate command message. The UE configuration update command message forthe UE network slicing configuration update may include: new configuredNSSAI for the serving PLMN; a mapping of the configured NSSAI to theconfigured NSSAI for the HPLMN; and/or the new configured NSSAI for theHPLMN.

In a possible third communication 520 from the UE 502 to the serving AMF506, the UE 502 may respond to the second communication 518 with a UEconfiguration update complete message to confirm the reception andsuccessful network slicing configuration in the UE 502.

The serving AMF 506 may update 522 its information to indicate that theUE 502 has been provided the configured NSSAI.

In a fourth communication 524 from the serving AMF 506 to the UDM/UDR510, the serving AMF 506 may initiate a procedure to perform a UEsubscription information update to inform the UDM/UDR 510 that the UE502 has been provided the configured NSSAI for the HPLMN. The servingAMF 506 may inform the UDM/UDR 510 about whether the whole list ofsubscribed S-NSSAIs has been provided to the UE 502, or whether only asingle default S-NSSAI value has been provided to the UE 502. Inaddition, the serving AMF 506 may include a device ID and/or anequipment ID (e.g. IMEI), so that the UDM/UDR 510 knows and stores thedevice ID and/or the equipment ID to which the configured NSSAI has beenprovided. Accordingly, the device ID and/or the equipment ID may be usedby the UDM/UDR 510 to determine whether a new device is used with thesame subscription profile (e.g., with the same SIM card). The UDM/UDR510 can either create a new entry for providing the configured NSSAI toa device having the device ID, or update an existing entry for thedevice ID.

The UDM/UDR 510 may update 526 the UE subscription information using theinformation received from the serving AMF 506.

After the configured NSSAI for the HPLMN or the configured NSSAI for theserving PLMN have been updated in the UE 502, in a fifth communication528 between the UE 502, the RAN 504, the serving AMF 506, the NSSF 508,and/or the UDM/UDR 510, the UE 502 may initiate a registration procedureas per TS 23.502 to signal a new requested NSSAI based on the newconfigured NSSAI for the HPLMN or the configured NSSAI for the servingPLMN parameters.

In certain embodiments, a UE may be provided with a slice configuration(e.g., configured NSSAI for serving VPLMN) in roaming configurations.

FIG. 6 is a schematic block diagram illustrating one embodiment ofcommunications 600 for signaling flow to provision a UE with a sliceconfiguration in a roaming configuration. The communications 600includes messages transmitted between a UE 602, a RAN 604, a servingvAMF 606, a PCF 608, an NSSF 610, and a UDM/UDR 612. As may beappreciated, each communication described herein may include one or moremessages.

In a first communication 614 transmitted from the UE 602 to the RAN 604,the UE 602 may send a NAS registration request message to the RAN 604that may include: a UE ID (e.g., SUPI); a registration type (e.g.,initial, mobility), and/or a requested NSSAI. The NAS registrationrequest message may be encapsulated in RRC signaling. In someembodiments, the RRC signaling contains a requested NSSAI. It someembodiments, the requested NSSAI is not included or is equal to zero.

In a second communication 616 transmitted from the RAN 604 to theserving vAMF 606, the RAN 604 may send the NAS registration requestmessage to the serving vAMF 606.

In a third communication 618 transmitted from the serving vAMF 606 tothe UDM/UDR 612, the serving vAMF 606 may request the UE subscriptioninformation from the UDM/UDR 612 via a UE subscription request. Forexample, the serving vAMF 606 may register with the UDM/UDR 612 using aNudm_UECM_Registration service.

In a fourth communication 620 transmitted from the UDM/UDR 612 to theserving vAMF 606, the serving vAMF 606 may retrieve access and mobilitysubscription data and SMF selection subscription data using a serviceNudm_SDM_Get, for example. In some embodiments, the UDM/UDR 612 includesin the fourth communication 620 an indication about whether theconfigured NSSAI for HPLMN has been provided to the UE 602. For example,this indication may be indicated by an IE having different values (e.g.,‘Configured NSSAI for HPLMN Provisioned’=TRUE (or FALSE)).

In certain embodiments, the configured NSSAI for the HPLMN may be sentfrom the UDM/UDR 612 to the serving vAMF 606. If the configured NSSAIfor the HPLMN is included in the UE's subscription information from theUDM/UDR 612, the configured NSSAI can be used as an indication to theserving vAMF 606 that the configured NSSAI for the HPLMN has beenprovided to the UE 602. If the configured NSSAI for the HPLMN is notincluded in the UE's subscription information from the UDM/UDR 612, thelack of the configured NSSAI may be used as indication to the servingvAMF 606 that the configured NSSAI for the HPLMN has not been providedto the UE 602.

If the NAS registration request message does not contain requestedNSSAI, and the registration type is “Initial Registration,” “MobilityRegistration Update,” or the like, the serving vAMF 606 determines 622that the UE 602 has not been provided with a configured NSSAI for acurrent PLMN. The serving vAMF 606 may decide to provide the UE 602 withthe configured NS SAI and/or send a corresponding request message to theNSSF 610.

It should be noted that the serving vAMF 606, in determining whether toprovide the UE 602 with the configured NSSAI, may take into account oneof the following conditions: 1) whether the UE 602 has been providedwith a configured NSSAI for a HPLMN. For example, if the configuredNSSAI for HPLMN=TRUE, the serving vAMF 606 may decide to provide the UEwith a configured NSSAI for a serving PLMN. One reason for the AMF toconsider this indication is as follows: if the “Configured NSSAI for theHPLMN” is not provided to the UE 602, then providing the configuredNSSAI for a current VPLMN may not make sense if there are VPLMN-specificS-NSSAI values that may map to S-NSSAI values from the HPLMN. In otherwords, mapping information for the configured NSSAI (e.g., ‘Mapping OfConfigured NSSAI’) and mapping information for allowed NSSAI (e.g.,‘Mapping Of Allowed NSSAI’) may not be provided to the UE 602. However,if the mapping information is not needed, then the serving vAMF 606and/or a vNSSF may derive and provide the UE 602 with a configured NSSAIfor a current PLMN (and allowed NSSAI); and/or 2) whether there is asingle subscribed S-NSSAI. If there is a single subscribed S-NSSAI, theserving vAMF 606 may omit providing the Configured NSSAI for the currentPLMN.

In some embodiments, the serving vAMF 606, based on local policiesand/or configuration, may derive the configured NSSAI and thecorresponding ‘Mapping Of Configured NSSAI’ information by itself Insuch embodiments, communications 624 through 628 may be omitted.

In a potential fifth communication 624 transmitted from the serving vAMF606 to the NSSF 610, the serving vAMF 606 sends to the NSSF 610 a sliceselection request (e.g., subscribed S-NSSAIs, a TAI, a PLMN ID of aSUPI, a request for allowed NSSAI, and/or a request for configuredNSSAI). If the serving vAMF 606 has decided to provide the UE 602 with aconfigured NSSAI for a serving PLMN, and the serving vAMF 606 (e.g.,based on local policies or configuration) is not able to derive and/orcreate the configured NSSAI for the current PLMN, the serving vAMF 606may send an indication to the NSSF 610 to request the NSSF 610 to createand/or derive a configured NSSAI for the UE 602 for the current PLMN. Insome embodiments, the indication may be called a ‘Request for ConfiguredNSSAI’ or the like.

In certain embodiments, the serving vAMF 606 may be able or may not beable to create allowed NSSAI for the UE 602 for a registration area. Ifthe serving vAMF 606, based on local policies and/or configuration inthe serving vAMF 606, is not able to create allowed NSSAI for the UE602, the serving vAMF 606 sends an indication to the NSSF 610 to requestthe NSSF 610 to create and/or derive an allowed NSSAI for the UE 602 fora current PLMN. In various embodiments, the indication can be called a‘Request for Allowed NSSAI’ or the like.

In some embodiments, the NSSF 610 (e.g. serving NSSF, vising NSSF) mayderive 626 information requested by the serving vAMF 606 in the fifthcommunication 624. Based on subscribed S-NSSAIs and SUPI's PLMN IDreceived from the serving vAMF 606, the NSSF 610 is able to determinethe configured NSSAI together with ‘Mapping Of Configured NSSAI’ andalso allowed NSSAI with ‘Mapping Of Allowed NSSAI’ for the UE 602. TheNSSF 610 may take into account the SLA agreements with the HPLMN inorder to derive the ‘Mapping Of Configured NSSAI’ information and the‘Mapping Of Allowed NSSAI’ information.

If needed, the NSSF in the VPLMN (e.g., vNSSF) may request informationfrom the NSSF in the HPLMN (e.g., hNSSF) to derive the configured NSSAItogether with mapping of configured NSSAI and allowed NSSAI with mappingof allowed NSSAI information. The vNSSF and the hNSSF exchange signalingover an N31 interface. In order to provide complete information to thevNSSF, the hNSSF may retrieve UE subscription information (e.g.,subscribed S-NSSAIs) from the UDM/UDR 612. The reason for the hNSSF toretrieve subscription information may be that the subscribed S-NSSAIssignaled from the serving vAMF 606 to vNSSF and further from vNSSF tohNSSF may not be the complete list of subscribed S-NSSAIs as stored inthe UDM/UDR 612. It should be noted that the information exchangebetween the NSSF (e.g. hNSSF) and UDM/UDR 612 may use enhancements tothe functionality of the NSSF and of the UDM/UDR 612.

In a potential sixth communication 628 transmitted from the NS SF 610 tothe serving vAMF 606, the NSSF 610 sends to the serving vAMF 606 a sliceselection response (e.g., a target AMF, a set or list of AMF addresses,allowed NSSAI, a mapping of allowed NS SAI, NSI IDs, NRF(s), a list ofrejected S-NSSAIs, cause values of rejected S-NSSAIs, configured NSSAI,and/or a mapping of configured NSSAI).

The NSSF 610 may create the information transmitted in the sixthcommunication 628 about the allowed NSSAI, mapping of allowed NSSAI,configured NSSAI, and/or mapping of configured NSSAI as describedherein.

In a seventh communication 630 between the UE 602, the RAN 604, theserving vAMF 606, the PCF 608, the NSSF 610, and/or the UDM/UDR,messages may be sent based on the registration procedure as described inTS 23.502.

In an eighth communication 632 from the serving vAMF 606 to the UE 602,the serving vAMF 606 may transmit a registration accept message to theUE 602.

In a ninth communication 634 from the serving vAMF 606 to the UE 602,the serving vAMF 606 may initiate a UE configuration update procedure inorder to update the UE network slicing configuration. The serving vAMF606 may provide the UE 602 with a new configured NSSAI for a servingPLMN which may be associated with mapping of the S-NSSAIs values fromthe configured NSSAI to the S-NSSAI values from the configured NSSAI forthe HPLMN. The UE network slicing configuration may contain: ‘ConfiguredNS SAI’ for the serving PLMN information and/or ‘Mapping Of ConfiguredNSSAI’ information.

In a potential tenth communication 636 from the UE 602 to the servingvAMF 606, the UE 602 may send a UE configuration update complete messageto the serving vAMF 606 if the UE configuration update indicationrequires acknowledgement of the UE configuration update command.

The serving vAMF 606 may update 638 a UE MM context and may store thenetwork slicing configuration information (e.g., received from the NSSF610), in particular the ‘Configured NSSAI’ and ‘Mapping Of ConfiguredNSSAI’ information. The UE MM context may be transferred to any otherAMF (or MME) during mobility procedures (IDLE mode or CONNECTED modemobility).

In various embodiments, the serving vAMF 606 first determines whether toprovide (or update) the UE 602 with configured NSSAI. If providing (orupdating) is needed, then the configured NSSAI for a serving PLMN (e.g.,VPLMN) is created either: (a) in the serving vAMF 606 or (b) in the NSSF610 (e.g., vNSSF) if the serving vAMF 606 is not able to create it basedon local policies (the serving vAMF 606 may explicitly request the NSSF610 to derive the configured NSSAI and/or the allowed NSSAI).

In certain embodiments, if the serving vAMF 606 (alone or together withthe NSSF 610) derives a configured NSSAI and/or the VPLMN mapsconfigured NSSAI information, the serving vAMF 606 may send this derivednetwork slicing configuration information to the UDM/UDR 612 for storingand for possible exposure to other NFs (e.g., other AMFs). Such networkslicing configuration information (e.g., configured NSSAIs) may bestored in the UDM/UDR 612 and exposed to other NFs if requested.

In some embodiments, in a non-roaming configuration, an AMF may create aconfigured NSSAI for a HPLMN and provide the configured NSSAI to a UE.Based on the subscription information, the AMF may indicate to the UE towhich PLMN IDs the configured NSSAI for the HPLMN may apply. A UDM/UDRmay provide the AMF additional configured NSSAIs for other PLMNs whichmay be provided to the UE as part of network slicing configurationinformation.

In various embodiments, in a roaming configuration, an AMF may requestan NSSF to create configured NSSAI for a serving PLMN associated withmapping of the configured NSSAI to configured NSSAI for the HPLMN. AUDM/UDR may send the configured NSSAI for the HPLMN to a serving AMF andthe serving AMF may include this information if exchanging informationwith the NSSF (e.g., visited NSSF). The NSSF may use the configuredNSSAI for the HPLMN also for creating a mapping of allowed NSSAI tocorresponding S-NSSAI values in the configured NSSAI for the HPLMN.

In certain embodiments, an AMF may determine to trigger providing orupdating a UE with a new configured NSSAI for a serving PLMN in thefollowing cases:

1) if a requested NSSAI is not included in a registration requestmessage and subscribed S-NSSAIs contain at least one value which is notused in the serving PLMN (e.g., PLMN-specific non-standard S-NSSAIvalue); or if the requested NSSAI is included in the registrationrequest message, but one or more of the S-NSSAI values are not known tothe AMF, the AMF may request the NSSF for resolution of the unknownvalues and the AMF (together with NSSF) may determine that theconfigured NSSAI for the serving PLMN is not correct and needs to beupdated; and

2) if there is an indication from a UDM about a change of subscribedS-NSSAIs or an indication with a new configured NSSAI for the HPLMN; orif the network slice availability has changed in the serving PLMN asspecified in clause 5.15.8, the NSSF may notify the AMF about the sliceavailability change and/or the NSSF may indicate a new configured NSSAI(and possibly allowed NSSAI) together with corresponding mappinginformation to the configured NSSAI for the HPLMN.

In some embodiments, configured NS SAI may be provided by a PCFinfrastructure. In such embodiments, if a UE sends a registrationrequest message to an AMF, the AMF interfaces with the PCF to obtain aconfigured NSSAI for the UE. Moreover, the AMF explicitly requests theconfigured NSSAI for this PLMN and the PCF includes an additional policywithin the UE policy content that may contain slice selection policiesin a PLMN.

FIG. 7 is a schematic block diagram illustrating one embodiment ofcommunications 700 for signaling flow to provision a UE with a sliceconfiguration via a PCF. The communications 700 includes messagestransmitted between a UE 702, a RAN 704, a serving AMF 706, a PCF 708,and a UDM/UDR 710. As may be appreciated, each communication describedherein may include one or more messages.

In a first communication 712 transmitted from the UE 702 to the RAN 704,the UE 702 may send a NAS registration request message to the RAN 704that may include: a UE ID (e.g., SUPI); a registration type (e.g.,initial, mobility), and/or a requested NSSAI. The NAS registrationrequest message may be encapsulated in RRC signaling. In someembodiments, the RRC signaling contains a requested NSSAI. It someembodiments, the requested NSSAI is not included or is equal to zero.

In a second communication 714 transmitted from the RAN 704 to theserving AMF 706, the RAN 704 may send the NAS registration requestmessage to the serving AMF 706.

In a third communication 716 transmitted from the serving AMF 706 to thePCF 708, the serving AMF 706 requests new UE policies from the PCF 708.The serving AMF 706 includes in the request that the UE 702 has noconfigured NSSAI. If the UE 702 is roaming, the serving AMF 706 sendsthe request to a V-PCF (e.g., visited PCF). The V-PCF forwards therequest to the H-PCF (e.g., home PCF). The serving AMF 706 mayexplicitly request the configured NSSAI for a current PLMN from the PCF708.

In a fourth communication 718 transmitted from the PCF 708 to theUDM/UDR 710, the PCF 708 (e.g., H-PCF) requests from the UDM/UDR 710subscribed NSSAI. If the UE 702 is roaming the PCF 708 includes aserving PLMN ID in the request.

In a fifth communication 720 transmitted from the UDM/UDR 710 to the PCF708, the UDM/UDR 710 provides subscription information including thesubscribed NSSAI. The UDM/UDR 710 may also provide a list of configuredNSSAI for each PLMN the operator has SLAs with and a configured NSSAI ofthe HPLMN.

The PCF 708 adds 722 the configured NSSAI of the HPLMN and theconfigured NSSAI list per PLMN within the PLMN slice selection policyincluded within the UE policy. The PCF 708 may also interact with anNSSF to generate this information. For example, the PCF 708 may requestthe NSSF to derive mapping information of the configured NSSAI for theVPLMN to the configured NSSAI for the HPLMN.

In a sixth communication 724 transmitted from the PCF 708 to the servingAMF 706, the PCF 708 provides the UE policy to the serving AMF 706. Ifthe UE 702 is roaming, the PCF 708 provides the UE policy to the V-PCF.The PCF 708 also includes the subscribed NSSAI provided by the UDM/UDR710. The V-PCF may add its own PLMN slice selection policy (e.g.,configured NSSAI). The V-PCF uses the subscribed NSSAI provided by theHPLMN to determine the configured NSSAI.

The serving AMF 706 determines 726 whether a UE policy should be sent tothe UE 702 and uses a configuration update procedure once registrationis complete.

In a seventh communication 728 transmitted from the serving AMF 706 tothe UE 702, the serving AMF 706 sends a registration accept includingthe allowed NSSAI.

In an eighth communication 730 transmitted from the serving AMF 706 tothe UE 702, the serving AMF 706 sends a UE configuration updateprocedure including the updated UE policy.

In certain embodiments, a PLMN slice selection policy may include thefollowing information: a list of PLMN slice selection policies inpriority order. Moreover, each policy may include the followinginformation: a PLMN ID, a configured NSSAI, and/or a mapping ofconfigured NSSAI to HPLMN configured NSSAI.

In some embodiments, if the UE 702 sends a registration request andcontains a PLMN slice selection policy, the UE 702 checks the PLMN IDand selects a highest priority policy of that PLMN. The UE 702 includesin the registration request only the NSSAIs within the configured NSSAI.

FIG. 8 is a flow chart diagram illustrating one embodiment of a method800 for NSSAI configuration. In some embodiments, the method 800 isperformed by an apparatus, such as the network unit 104. In certainembodiments, the method 800 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 800 may include determining 802 a configured network sliceselection assistance information for a public land mobile network for aremote unit 102 in response to a trigger from an access and mobilitymanagement function. In such an embodiment, the access and mobilitymanagement function, a network slice selection function, or acombination thereof determines the configured network slice selectionassistance information. In certain embodiments, the method 800 includesproviding 804 the configured network slice selection assistanceinformation to the remote unit 102 via the access and mobilitymanagement function.

In certain embodiments, the access and mobility management functiondetermines the configured network slice selection assistanceinformation. In some embodiments, the access and mobility managementfunction determines the configured network slice selection assistanceinformation in response to not receiving information about network sliceselection assistance information in a registration request. In variousembodiments, the access and mobility management function determines theconfigured network slice selection assistance information in response todetermining that the remote unit 102 should be provided the configurednetwork slice selection assistance information.

In one embodiment, the access and mobility management functiondetermines the configured network slice selection assistance informationbased on an indication from a subscription repository about updatednetwork slice subscription data related to the remote unit 102. Incertain embodiments, the network slice selection function determines theconfigured network slice selection assistance information. In someembodiments, the network slice selection function determines theconfigured network slice selection assistance information in response toa request from the access and mobility management function not includinga requested network slice selection assistance information.

In various embodiments, the method 800 further comprises receiving anindication that subscribed network slice selection assistanceinformation has changed, wherein the configured network slice selectionassistance information is provided to the remote unit 102 in response tothe change in the subscribed network slice selection assistanceinformation. In one embodiment, the indication is received from aunified data management function. In certain embodiments, the unifieddata management function tracks whether the subscribed network sliceselection assistance information has resulted in updating of theconfigured network slice selection assistance information in the remoteunit.

In some embodiments, the method 800 further comprises receiving anindication from a unified data management function that the configurednetwork slice selection assistance information is no longer valid. Invarious embodiments, the method 800 further comprises receiving anacknowledgement from the remote unit 102 indicating that the configurednetwork slice selection assistance information is updated at the remoteunit 102. In one embodiment, the method 800 further comprisestransmitting information to a unified data management functionindicating that the configured network slice selection assistanceinformation is updated at the remote unit 102.

FIG. 9 is a flow chart diagram illustrating another embodiment of amethod 900 for NSSAI configuration. In some embodiments, the method 900is performed by an apparatus, such as the remote unit 102. In certainembodiments, the method 900 may be performed by a processor executingprogram code, for example, a microcontroller, a microprocessor, a CPU, aGPU, an auxiliary processing unit, a FPGA, or the like.

The method 900 may include receiving 902, at a remote unit 102, aconfigured network slice selection assistance information for a publicland mobile network via an access and mobility management function. Insuch an embodiment, the access and mobility management function, anetwork slice selection function, or a combination thereof determinesthe configured network slice selection assistance information inresponse to a trigger from the access and mobility management function.

In certain embodiments, the access and mobility management functiondetermines the configured network slice selection assistanceinformation. In some embodiments, the access and mobility managementfunction determines the configured network slice selection assistanceinformation in response to not receiving information about network sliceselection assistance information in a registration request. In variousembodiments, the access and mobility management function determines theconfigured network slice selection assistance information in response todetermining that the remote unit 102 should be provided the configurednetwork slice selection assistance information.

In one embodiment, the access and mobility management functiondetermines the configured network slice selection assistance informationbased on an indication from a subscription repository about updatednetwork slice subscription data related to the remote unit 102. Incertain embodiments, the network slice selection function determines theconfigured network slice selection assistance information. In someembodiments, the network slice selection function determines theconfigured network slice selection assistance information in response toa request from the access and mobility management function not includinga requested network slice selection assistance information.

In various embodiments, the method 900 further comprises transmitting anacknowledgement from the remote unit 102 indicating that the configurednetwork slice selection assistance information is updated at the remoteunit 102.

FIG. 10 is a flow chart diagram illustrating a further embodiment of amethod 1000 for NSSAI configuration. In some embodiments, the method1000 is performed by an apparatus, such as the remote unit 102. Incertain embodiments, the method 1000 may be performed by a processorexecuting program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 1000 may include receiving 1002, at a remote unit 102, firstconfigured network slice selection assistance information for a firstpublic land mobile network. In some embodiments, the method 1000includes storing 1004, at the remote unit 102, the first configurednetwork slice selection assistance information for the first public landmobile network. In certain embodiments, the method 1000 includestransmitting 1006 a first acknowledgment in response to receiving thefirst configured network slice selection assistance information. In suchembodiments, the first acknowledgment indicates that the firstconfigured network slice selection assistance information was received.In various embodiments, the method 1000 includes receiving 1008, at theremote unit 102, second configured network slice selection assistanceinformation for a second public land mobile network. In one embodiment,the method 1000 includes storing 1010, at the remote unit 102, thesecond configured network slice selection assistance information for thesecond public land mobile network. In some embodiments, the method 1000includes transmitting 1012 a second acknowledgment in response toreceiving the second configured network slice selection assistanceinformation. In such embodiments, the second acknowledgment indicatesthat the second configured network slice selection assistanceinformation was received.

FIG. 11 is a flow chart diagram illustrating yet another embodiment of amethod 1100 for NSSAI configuration. In some embodiments, the method1100 is performed by an apparatus, such as the network unit 104. Incertain embodiments, the method 1100 may be performed by a processorexecuting program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 1100 may include determining 1102, within a unified datamanagement, function a default network slice selection assistanceinformation for a public land mobile network for a remote unit 102. Asused herein, a default network slice selection assistance informationfor a public land mobile network may be a default network sliceselection assistance information for any public land mobile network. Forexample, a default network slice selection assistance information for apublic land mobile network may be a default network slice selectionassistance information for all public land mobile networks (e.g., thereis no specific network slice selection assistance information for aparticular public land mobile network). In some embodiments, the method1100 includes providing 1104 the default network slice selectionassistance information to the remote unit 102.

In certain embodiments, the method 1100 further comprises receiving anacknowledgment indicating that the remote unit 102 is updated with thedefault network slice selection assistance information. In someembodiments, the method 1100 further comprises receiving informationindicating a subscription change. In various embodiments, the method1100 further comprises updating the default network slice selectionassistance information in response to receiving the informationindicating the subscription change.

In one embodiment, the method 1100 further comprises providing theupdated default network slice selection assistance information to theremote unit 102. In certain embodiments, providing the default networkslice selection assistance information to the remote unit 102 comprisesproviding the default network slice selection assistance information tothe remote unit 102 via an access and mobility management function. Insome embodiments, the default network slice selection assistanceinformation is included in a non-access stratum signaling message sentfrom an access and mobility management function. In various embodiments,in response to providing the default network slice selection assistanceinformation, stored default network slice selection assistanceinformation is updated by the remote unit 102.

In one embodiment, determining the default network slice selectionassistance information for a public land mobile network for the remoteunit 102 comprises determining the default network slice selectionassistance information for public land mobile networks (e.g., any publicland mobile networks) for which no specific (e.g., no other) configurednetwork slice selection assistance information has been provided to theremote unit 102.

FIG. 12 is a flow chart diagram illustrating a yet further embodiment ofa method 1200 for NSSAI configuration. In some embodiments, the method1200 is performed by an apparatus, such as the remote unit 102. Incertain embodiments, the method 1200 may be performed by a processorexecuting program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 1200 may include receiving 1202, at a remote unit 102, adefault network slice selection assistance information for a public landmobile network. In such an embodiment, a unified data managementfunction determines the default network slice selection assistanceinformation and provides the default network slice selection assistanceinformation to the remote unit 102.

In certain embodiments, the method 1200 further comprises transmittingan acknowledgment indicating that the remote unit 102 is updated withthe default network slice selection assistance information. In someembodiments, the unified data management function provides the defaultnetwork slice selection assistance information to the remote unit 102via an access and mobility management function. In various embodiments,the default network slice selection assistance information is includedin a non-access stratum signaling message sent from an access andmobility management function. In one embodiment, the method 1200 furthercomprises, in response to receiving the default network slice selectionassistance information, updating stored default network slice selectionassistance information of the remote unit 102.

In certain embodiments, the unified data management function determinesthe default network slice selection assistance information bydetermining the default network slice selection assistance informationfor public land mobile networks (e.g., any public land mobile networks)for which no specific (e.g., no other) configured network sliceselection assistance information has been provided to the remote unit102.

In one embodiment, a method comprises: determining a configured networkslice selection assistance information for a public land mobile networkfor a remote unit in response to a trigger from an access and mobilitymanagement function, wherein the access and mobility managementfunction, a network slice selection function, or a combination thereofdetermines the configured network slice selection assistanceinformation; and providing the configured network slice selectionassistance information to the remote unit via the access and mobilitymanagement function.

In certain embodiments, the access and mobility management functiondetermines the configured network slice selection assistanceinformation.

In some embodiments, the access and mobility management functiondetermines the configured network slice selection assistance informationin response to not receiving information about network slice selectionassistance information in a registration request.

In various embodiments, the access and mobility management functiondetermines the configured network slice selection assistance informationin response to determining that the remote unit should be provided theconfigured network slice selection assistance information.

In one embodiment, the access and mobility management functiondetermines the configured network slice selection assistance informationbased on an indication from a subscription repository about updatednetwork slice subscription data related to the remote unit.

In certain embodiments, the network slice selection function determinesthe configured network slice selection assistance information.

In some embodiments, the network slice selection function determines theconfigured network slice selection assistance information in response toa request from the access and mobility management function not includinga requested network slice selection assistance information.

In various embodiments, the method further comprises receiving anindication that subscribed network slice selection assistanceinformation has changed, wherein the configured network slice selectionassistance information is provided to the remote unit in response to thechange in the subscribed network slice selection assistance information.

In one embodiment, the indication is received from a unified datamanagement function.

In certain embodiments, the unified data management function trackswhether the subscribed network slice selection assistance informationhas resulted in updating of the configured network slice selectionassistance information in the remote unit.

In some embodiments, the method further comprises receiving anindication from a unified data management function that the configurednetwork slice selection assistance information is no longer valid.

In various embodiments, the method further comprises receiving anacknowledgement from the remote unit indicating that the configurednetwork slice selection assistance information is updated at the remoteunit.

In one embodiment, the method further comprises transmitting informationto a unified data management function indicating that the configurednetwork slice selection assistance information is updated at the remoteunit.

In one embodiment, an apparatus comprises: a processor that determines aconfigured network slice selection assistance information for a publicland mobile network for a remote unit in response to a trigger from anaccess and mobility management function, wherein the access and mobilitymanagement function, a network slice selection function, or acombination thereof determines the configured network slice selectionassistance information; and a transmitter that provides the configurednetwork slice selection assistance information to the remote unit viathe access and mobility management function.

In certain embodiments, the access and mobility management functiondetermines the configured network slice selection assistanceinformation.

In some embodiments, the access and mobility management functiondetermines the configured network slice selection assistance informationin response to not receiving information about network slice selectionassistance information in a registration request.

In various embodiments, the access and mobility management functiondetermines the configured network slice selection assistance informationin response to determining that the remote unit should be provided theconfigured network slice selection assistance information.

In one embodiment, the access and mobility management functiondetermines the configured network slice selection assistance informationbased on an indication from a subscription repository about updatednetwork slice subscription data related to the remote unit.

In certain embodiments, the network slice selection function determinesthe configured network slice selection assistance information.

In some embodiments, the network slice selection function determines theconfigured network slice selection assistance information in response toa request from the access and mobility management function not includinga requested network slice selection assistance information.

In various embodiments, the apparatus further comprises a receiver thatreceives an indication that subscribed network slice selectionassistance information has changed, wherein the configured network sliceselection assistance information is provided to the remote unit inresponse to the change in the subscribed network slice selectionassistance information.

In one embodiment, the indication is received from a unified datamanagement function.

In certain embodiments, the unified data management function trackswhether the subscribed network slice selection assistance informationhas resulted in updating of the configured network slice selectionassistance information in the remote unit.

In some embodiments, the apparatus further comprises a receiver thatreceives an indication from a unified data management function that theconfigured network slice selection assistance information is no longervalid.

In various embodiments, the apparatus further comprises a receiver thatreceives an acknowledgement from the remote unit indicating that theconfigured network slice selection assistance information is updated atthe remote unit.

In one embodiment, the transmitter transmits information to a unifieddata management function indicating that the configured network sliceselection assistance information is updated at the remote unit.

In one embodiment, a method comprises: receiving, at a remote unit, aconfigured network slice selection assistance information for a publicland mobile network via an access and mobility management function,wherein the access and mobility management function, a network sliceselection function, or a combination thereof determines the configurednetwork slice selection assistance information in response to a triggerfrom the access and mobility management function.

In certain embodiments, the access and mobility management functiondetermines the configured network slice selection assistanceinformation.

In some embodiments, the access and mobility management functiondetermines the configured network slice selection assistance informationin response to not receiving information about network slice selectionassistance information in a registration request.

In various embodiments, the access and mobility management functiondetermines the configured network slice selection assistance informationin response to determining that the remote unit should be provided theconfigured network slice selection assistance information.

In one embodiment, the access and mobility management functiondetermines the configured network slice selection assistance informationbased on an indication from a subscription repository about updatednetwork slice subscription data related to the remote unit.

In certain embodiments, the network slice selection function determinesthe configured network slice selection assistance information.

In some embodiments, the network slice selection function determines theconfigured network slice selection assistance information in response toa request from the access and mobility management function not includinga requested network slice selection assistance information.

In various embodiments, the method further comprises transmitting anacknowledgement from the remote unit indicating that the configurednetwork slice selection assistance information is updated at the remoteunit.

In one embodiment, an apparatus comprises: a receiver that receives aconfigured network slice selection assistance information for a publicland mobile network via an access and mobility management function,wherein the access and mobility management function, a network sliceselection function, or a combination thereof determines the configurednetwork slice selection assistance information in response to a triggerfrom the access and mobility management function.

In certain embodiments, the access and mobility management functiondetermines the configured network slice selection assistanceinformation.

In some embodiments, the access and mobility management functiondetermines the configured network slice selection assistance informationin response to not receiving information about network slice selectionassistance information in a registration request.

In various embodiments, the access and mobility management functiondetermines the configured network slice selection assistance informationin response to determining that the apparatus should be provided theconfigured network slice selection assistance information.

In one embodiment, the access and mobility management functiondetermines the configured network slice selection assistance informationbased on an indication from a subscription repository about updatednetwork slice subscription data related to the apparatus.

In certain embodiments, the network slice selection function determinesthe configured network slice selection assistance information.

In some embodiments, the network slice selection function determines theconfigured network slice selection assistance information in response toa request from the access and mobility management function not includinga requested network slice selection assistance information.

In various embodiments, the apparatus further comprises a transmitterthat transmits an acknowledgement indicating that the configured networkslice selection assistance information is updated at the apparatus.

In one embodiment, a method comprises: receiving, at a remote unit,first configured network slice selection assistance information for afirst public land mobile network; storing, at the remote unit, the firstconfigured network slice selection assistance information for the firstpublic land mobile network; transmitting a first acknowledgment inresponse to receiving the first configured network slice selectionassistance information, wherein the first acknowledgment indicates thatthe first configured network slice selection assistance information wasreceived; receiving, at the remote unit, second configured network sliceselection assistance information for a second public land mobilenetwork; storing, at the remote unit, the second configured networkslice selection assistance information for the second public land mobilenetwork; and transmitting a second acknowledgment in response toreceiving the second configured network slice selection assistanceinformation, wherein the second acknowledgment indicates that the secondconfigured network slice selection assistance information was received.

In one embodiment, an apparatus comprises: a receiver that receivesfirst configured network slice selection assistance information for afirst public land mobile network; a processor that stores the firstconfigured network slice selection assistance information for the firstpublic land mobile network; a transmitter that transmits a firstacknowledgment in response to receiving the first configured networkslice selection assistance information, wherein the first acknowledgmentindicates that the first configured network slice selection assistanceinformation was received, wherein: the receiver receives secondconfigured network slice selection assistance information for a secondpublic land mobile network; the processor stores the second configurednetwork slice selection assistance information for the second publicland mobile network; and the transmitter transmits a secondacknowledgment in response to receiving the second configured networkslice selection assistance information, wherein the secondacknowledgment indicates that the second configured network sliceselection assistance information was received.

In one embodiment, a method comprises: determining, within a unifieddata management function, a default network slice selection assistanceinformation for a public land mobile network for a remote unit; andproviding the default network slice selection assistance information tothe remote unit.

In certain embodiments, the method further comprises receiving anacknowledgment indicating that the remote unit is updated with thedefault network slice selection assistance information.

In some embodiments, the method further comprises receiving informationindicating a subscription change.

In various embodiments, the method further comprises updating thedefault network slice selection assistance information in response toreceiving the information indicating the subscription change.

In one embodiment, the method further comprises providing the updateddefault network slice selection assistance information to the remoteunit.

In certain embodiments, providing the default network slice selectionassistance information to the remote unit comprises providing thedefault network slice selection assistance information to the remoteunit via an access and mobility management function.

In some embodiments, the default network slice selection assistanceinformation is included in a non-access stratum signaling message sentfrom an access and mobility management function.

In various embodiments, in response to providing the default networkslice selection assistance information, stored default network sliceselection assistance information is updated by the remote unit.

In one embodiment, determining the default network slice selectionassistance information for a public land mobile network for the remoteunit comprises determining the default network slice selectionassistance information for public land mobile networks for which nospecific configured network slice selection assistance information hasbeen provided to the remote unit.

In one embodiment, an apparatus comprises: a processor that determines,within a unified data management function, a default network sliceselection assistance information for a public land mobile network for aremote unit; and a transmitter that provides the default network sliceselection assistance information to the remote unit.

In certain embodiments, the method further comprises a receiver thatreceives an acknowledgment indicating that the remote unit is updatedwith the default network slice selection assistance information.

In some embodiments, the apparatus further comprises a receiver thatreceives information indicating a subscription change.

In various embodiments, the processor updates the default network sliceselection assistance information in response to receiving theinformation indicating the subscription change.

In one embodiment, the transmitter provides the updated default networkslice selection assistance information to the remote unit.

In certain embodiments, the transmitter providing the default networkslice selection assistance information to the remote unit comprises thetransmitter providing the default network slice selection assistanceinformation to the remote unit via an access and mobility managementfunction.

In some embodiments, the default network slice selection assistanceinformation is included in a non-access stratum signaling message sentfrom an access and mobility management function.

In various embodiments, in response to the transmitter providing thedefault network slice selection assistance information, stored defaultnetwork slice selection assistance information is updated by the remoteunit.

In one embodiment, the processor determines the default network sliceselection assistance information for a public land mobile network forthe remote unit by determining the default network slice selectionassistance information for public land mobile networks for which nospecific configured network slice selection assistance information hasbeen provided to the remote unit.

In one embodiment, a method comprises: receiving, at a remote unit, adefault network slice selection assistance information for a public landmobile network, wherein a unified data management function determinesthe default network slice selection assistance information and providesthe default network slice selection assistance information to the remoteunit.

In certain embodiments, the method further comprises transmitting anacknowledgment indicating that the remote unit is updated with thedefault network slice selection assistance information.

In some embodiments, the unified data management function provides thedefault network slice selection assistance information to the remoteunit via an access and mobility management function.

In various embodiments, the default network slice selection assistanceinformation is included in a non-access stratum signaling message sentfrom an access and mobility management function.

In one embodiment, the method further comprises, in response toreceiving the default network slice selection assistance information,updating stored default network slice selection assistance informationof the remote unit.

In certain embodiments, the unified data management function determinesthe default network slice selection assistance information bydetermining the default network slice selection assistance informationfor public land mobile networks for which no specific configured networkslice selection assistance information has been provided to the remoteunit.

In one embodiment, an apparatus comprises: a receiver that receives adefault network slice selection assistance information for a public landmobile network, wherein a unified data management function determinesthe default network slice selection assistance information and providesthe default network slice selection assistance information to theapparatus.

In certain embodiments, the apparatus further comprises a transmitterthat transmits an acknowledgment indicating that the apparatus isupdated with the default network slice selection assistance information.

In some embodiments, the unified data management function provides thedefault network slice selection assistance information to the apparatusvia an access and mobility management function.

In various embodiments, the default network slice selection assistanceinformation is included in a non-access stratum signaling message sentfrom an access and mobility management function.

In one embodiment, the apparatus further comprises a processor that, inresponse to the receiver receiving the default network slice selectionassistance information, updates stored default network slice selectionassistance information of the apparatus.

In certain embodiments, the unified data management function determinesthe default network slice selection assistance information bydetermining the default network slice selection assistance informationfor public land mobile networks for which no specific configured networkslice selection assistance information has been provided to theapparatus.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. An apparatus for wireless communication, the apparatus comprising: aprocessor; and a memory coupled with the processor, the memorycomprising instructions executable by the processor to cause theapparatus to: determine a configured network slice selection assistanceinformation for a public land mobile network associated with a userequipment (UE); and provide, to the UE, the configured network sliceselection assistance information.
 2. The apparatus of claim 1, whereinthe apparatus comprises an access and mobility management function(AMF), and wherein the instructions are executable by the processor tocause the AMF to determine the configured network slice selectionassistance information.
 3. The apparatus of claim 1, wherein theinstructions are further executable by the processor to cause theapparatus to: receive, from a network slice selection function (NSSF),the configured network slice selection assistance information.
 4. Theapparatus of claim 1, wherein the instructions are further executable bythe processor to cause the apparatus to: determine the configurednetwork slice selection assistance information for the public landmobile network based at least in part on no reception of a requestednetwork slice selection assistance information.
 5. The apparatus ofclaim 1, wherein the instructions are further executable by theprocessor to cause the apparatus to: determine the configured networkslice selection assistance information for the public land mobilenetwork based at least in part on a requested network slice selectionassistance information being invalid for the public land mobile network.6. The apparatus of claim 1, wherein the instructions are furtherexecutable by the processor to cause the apparatus to: provide, to theUE, the configured network slice selection assistance information basedat least in part on a change to one or more subscribed single networkslice selection assistance information.
 7. The apparatus of claim 1,wherein the instructions are further executable by the processor tocause the apparatus to: receive an indication, from a unified datamanagement function (UDM), of a change to one or more subscribed singlenetwork slice selection assistance information, wherein to provide, tothe UE, the configured network slice selection assistance information isbased at least in part on the received indication, from the UDM, of thechange to the one or more subscribed single network slice selectionassistance information.
 8. The apparatus of claim 7, wherein theinstructions are further executable by the processor to cause theapparatus to: receive an acknowledgment from the UE in response to theprovided configured network slice selection assistance information. 9.The apparatus of claim 7, wherein the instructions are furtherexecutable by the processor to cause the apparatus to: transmit, to theUDM, an indication of successful provisioning of the configured networkslice selection assistance information.
 10. The apparatus of claim 1,wherein the public land mobile network comprises a serving public landmobile network.
 11. A method of wireless communication at a networkentity, the method comprising: determining a configured network sliceselection assistance information for a public land mobile networkassociated with a user equipment (UE); and providing, to the UE, theconfigured network slice selection assistance information.
 12. Themethod of claim 11, wherein the network entity comprises an access andmobility management function (AMF).
 13. The method of claim 11, furthercomprising: receiving, from a network slice selection function (NSSF),the configured network slice selection assistance information.
 14. Themethod of claim 11, further comprising: determining the configurednetwork slice selection assistance information for the public landmobile network based at least in part on no reception of a requestednetwork slice selection assistance information.
 15. The method of claim11, further comprising: determining the configured network sliceselection assistance information for the public land mobile networkbased at least in part on a requested network slice selection assistanceinformation being invalid for the public land mobile network.
 16. Themethod of claim 11, further comprising: providing, to the UE, theconfigured network slice selection assistance information based at leastin part on a change to one or more subscribed single network sliceselection assistance information.
 17. An apparatus for wirelesscommunication, the apparatus comprising: a processor; and a memorycoupled with the processor, the memory comprising instructionsexecutable by the processor to cause the apparatus to: determine aconfigured network slice selection assistance information for a publicland mobile network associated with a user equipment (UE); and transmit,to an access and mobility management function (AMF), the configurednetwork slice selection assistance information.
 18. The apparatus ofclaim 17, wherein the apparatus comprises a network slice selectionfunction (NSSF), and wherein the instructions are further executable bythe processor to cause the NSSF to determine the configured networkslice selection assistance information.
 19. An apparatus for wirelesscommunication, the apparatus comprising: a processor; and a memorycoupled with the processor, the memory comprising instructionsexecutable by the processor to cause the apparatus to: setting a flagindicative of a change to a user equipment (UE) subscription based atleast in part on a change to a subscribed network slice selectionassistance information for a UE; transmitting, to an access and mobilitymanagement function (AMF), an indication of the change to the UEsubscription and a configured network slice selection assistanceinformation; receiving an indication of successful provisioning of theconfigured network slice selection assistance information; and updatingthe set flag based at least in prat on the successful provisioning ofthe configured network slice selection assistance information.
 20. Theapparatus of claim 19, wherein the apparatus comprises a unified datamanagement function (UDM).